feat: publish egress events to cf queue#191
Merged
Conversation
fforbeck
force-pushed
the
feat/batch-egress-events
branch
from
151c208 to
336eec5
Compare
fforbeck
force-pushed
the
feat/batch-egress-events
branch
from
336eec5 to
ff72d89
Compare
alanshaw
pushed a commit
that referenced
this pull request
Nov 19, 2025
🤖 I have created a release *beep* *boop* --- ## [2.32.0](v2.31.2...v2.32.0) (2025-11-18) ### Features * publish egress events to cf queue ([#191](#191)) ([28dc194](28dc194)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR refactors the egress tracking system to use asynchronous batch processing instead of synchronous invocation execution. The freeway gateway now serializes egress tracking invocations and sends them to a Cloudflare Queue, where the egress-consumer processes them in batches before forwarding to the upload-api in a CAR with multiple invocations.
Key Changes
Freeway Gateway (Producer)
Modified the egress tracking middleware to serialize invocations instead of executing them immediately:
FF_EGRESS_TRACKER_ENABLED&FF_EGRESS_TRACKER_ROLLOUT_PERCENTAGEFlow
Additional Changes
devpackagespackage-lock.json